VHS Data Forwarding

The VHS Data Forwarding feature allows history data to be copied and pushed from a source VHS to up to three destination services. This allows the destination service(s) to serve as a long term repository for historical data.

Forwarding Data to a Destination VHS for Long-Term Storage

To use a destination VHS as a long-term storage solution, set its minimum retention period to a value greater than that of the source VHS. This allows the destination VHS to serve as a long-term historian while the source VHS can be configured to meet local needs.

One of the required configuration keywords of a VHS is its minimum retention period (MINIMUM_EXPIRE_DAYS). This sets the minimum number of days data is stored in the VHS. Points also have a retention property (Keep values within last) that specifies the period of time (in number of days) prior to now that CygNet will keep data points in the VHS. If both options are active, the longer of the two retention periods will take precedence.

With destination services, the minimum retention is useful for setting the retention of the destination site to a period longer than that of the source site. For example, the field office may need history values as far back as one year (365 days) but the corporate office may want to keep data for four years. As such, the destination VHS at the corporate office can be configured for a minimum retention of 1460 days.

Data Forwarding Considerations

• The VHS is the only service with Data Forwarding.
• The source VHS pushes data to the destination VHS in compressed blocks. Up to three separate destination services can be specified. The destination VHS may be on the same host server or on a different host server.
• A destination service can be any VHS on any Domain ID, including the same Domain ID as the source service.
• Both the source VHS and the destination VHS are live sources of data. Either source can be accessed for data display, trending, reports, etc. Typically the source VHS is configured and used for local data needs. The destination VHS is used for long-term storage and corporate reporting.
• Unlike replicated services, a destination VHS receiving forwarded data is not read-only. A user’s ability to read/write depends on the security of the destination VHS.
• Only data added to a VHS after Data Forwarding is started is pushed to the destination VHS. To backfill the destination VHS you must use the VHS Import/Export Utility.
• Data deleted from the source VHS using the VHS Data Thinner Utility, will also be deleted from the destination VHS service.

In a multi-host environment, CygNet Software recommends that a destination VHS only receive data forwarded from a single source to ease recovery in case of a service failure. If the source VHS fails, the data files from the destination service can be copied into the source service’s folder. If two source services are forwarding data to the same destination VHS and one of the source services fails, you would have to export the data from the destination service back to the source service. This is a more time consuming task.

Data Forwarding and Redundancy

Both the active and standby VHS in a Redundancy server pair can be configured for VHS data forwarding. This allows an active service in a redundancy pair to forward data to another destination VHS keeping both services in sync. While this configuration allows the standby VHS in the redundancy pair to be configured for data forwarding, forwarding will be ignored and no data will be pushed unless the VHS is the active service of the pair.

More:

How VHS Data Forwarding Works

Sample Forwarding Implementation

Configuring VHS Data Forwarding

Monitoring VHS Data Forwarding